﻿<html DIR="LTR" xmlns:tool="http://www.microsoft.com/tooltip" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:ddue="http://ddue.schemas.microsoft.com/authoring/2003/5" xmlns:MSHelp="http://msdn.microsoft.com/mshelp">
  <head>
    <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=utf-8" />
    <META NAME="save" CONTENT="history" />
    <title>Microsoft SQL Server 2008 R2 Release Notes: August 2009 CTP</title>
    
    
    
    <style TYPE="text/css">
body
{
background: #FFFFFF;
color: #000000;
font-family:    Verdana;
font-size: medium;
font-style: normal;
font-weight: normal;
margin-top: 0;
margin-bottom:  0;
margin-left:    0;
margin-right:   0;
width:  100%;
}

div.#mainSection
{
font-size: 70%;
width: 100%;
padding-left:    10;
margin-right: 10;
}

div.#mainBody
{
font-size: 90%;
margin-top: 10;
padding-bottom: 20;
}

div.#header
{
background-color: #D2D2D2;
padding-top:    0;
padding-bottom: 0;
padding-left:   10;
padding-right:  0;
width:          100%;
}

div.#header table
{
border-bottom-color: #C8CDDE;
border-bottom-style: solid;
border-bottom-width: 1;
width:  100%;
}

span.#runningHeaderText
{
color: #003399;
font-size: 90%;
}

span.#nsrTitle
{
/*    color: #003399;*/
font-size: 120%;
font-weight: 600;
}

div.#header table td
{
color: #000000;
font-size: 70%;
margin-top: 0;
margin-bottom:  0;
padding-right: 20;
}

div.#header table tr.#headerTableRow3 td
{
padding-bottom: 2;
padding-top: 5;
}

div.#header table.#bottomTable
{
border-top-color: #FFFFFF;
border-top-style: solid;
border-top-width: 1;
text-align: left;
}

div.#footer
{
font-size: 90%;
margin-top: 0;
margin-bottom:  0;
margin-left:    -5;
margin-right:   0;
padding-top:    2;
padding-bottom: 2;
padding-left:   0;
padding-right:  0;
width:  100%;
}

hr.#footerHR
{
border-bottom-color: #EEEEFF;
border-bottom-style: solid;
border-bottom-width: 1;
border-top-color: C8CDDE;
border-top-style: solid;
border-top-width: 1;
height: 3;
color: #D2D2D2;
}

div.section
{
padding-top:    2;
padding-bottom: 2;
padding-right:  15;
width:  100%;
}

.heading
{
color:          #000000;
font-weight:    bold;
margin-top:     18;
margin-bottom:  8;
}

h1.heading
{
color: #000000;
font-size:  150%;
}

.subHeading
{
color:          #000000;
font-weight:    bold;
font-size:      150%;
margin-bottom:  4;
}

h2.subHeading
{
color:          #000000;
font-weight:    bold;
font-size:      130%;
}
h3.subHeading
{
color:  #000000;
font-size: 125%;
font-weight: bold;
}

h4.subHeading
{
color: #000000;
font-size: 110%;
font-weight: bold;
}

h4.procedureHeading
{
color: #000080;
font-size: 110%;
font-weight: bold;
}

h5.subHeading
{
color: #000000;
font-size: 100%;
font-weight: bold;
}

img
{
padding-bottom: 10;
}

img.toggle
{
border: 0;
margin-right: 5;
padding-bottom: 10;
}

img.copyCodeImage
{
border: 0;
margin: 1;
margin-right: 3;
padding-bottom: 10;
}

img.downloadCodeImage
{
border: 0;
margin-right: 3;
padding-bottom: 10;
}

img.viewCodeImage
{
border: 0;
margin-right: 3;
padding-bottom: 10;
}

img.note
{
border: 0;
margin-right: 3;
padding-bottom: 10;
}

img.#membersOptionsFilterImage
{
border: 0;
margin-left: 10;
vertical-align: middle;
padding-bottom: 10;
}

img.#toggleAllImage
{
margin-left: 4;
vertical-align: middle;
padding-bottom: 10;
}

div.#mainSection table
{
border: 0;
font-size: 100%;
width:  100%;
margin-top: 5px;
margin-bottom: 15px;
}

div.#mainSection table tr
{
vertical-align: top;
}

div.#mainSection table th
{
text-align: left;
background: #D8D8D8;
border-bottom-color: #D8D8D8;
border-bottom-style: solid;
border-bottom-width: 1;
color: #000000;
padding-left: 5;
padding-right: 5;
}

div.#mainSection table td
{
background: #F2F2F2;
border-top-color: #D8D8D8;
border-top-style: solid;
border-top-width: 1;
padding-left: 5;
padding-right: 5;
}

div.#mainSection table td.imageCell
{
white-space: nowrap;
}

div.code
{
width: 98%;
}

div.code table
{
border: 0;
font-size: 95%;
margin-bottom: 5;
width: 100%
}

div.code table th
{
text-align: left;
background: #D8D8D8;
border-bottom-color: #D8D8D8;
border-bottom-style: solid;
border-bottom-width: 1;
color: #000000;
font-weight: bold;
padding-left: 5;
padding-right: 5;
}

div.code table td
{
background: #CCCCCC;
border-top-color: #D8D8D8;
border-top-style: solid;
border-top-width: 1;
padding-left: 5;
padding-right: 5;
padding-top: 5;
}

div.alert
{
margin-left: 10;
width: 98%;
}

div.alert table
{
border: 1;
font-size: 100%;
width:  100%;
border: solid 1 #DEDFEF;
}

div.alert table th
{
text-align: left;
background: #D8D8D8;
border-bottom-width: 0;
color: #000000;
padding-left: 5;
padding-right: 5;
border: solid 1 #DEDFEF;
}

div.alert table td
{
background: #FFFFFF;
border-top-color: #D8D8D8;
border-top-style: solid;
border-top-width: 1;
padding-left: 5;
padding-right: 5;
border: solid 1 #DEDFEF;
}

span.copyCode
{
color: #0000ff;
font-size: 90%;
font-weight: normal;
cursor: hand;
float: right;
display: inline;
text-align: right;
}

.downloadCode
{
color: #0000ff;
font-size: 90%;
font-weight: normal;
cursor: hand;
}

.viewCode
{
color: #0000ff;
font-size: 90%;
font-weight: normal;
cursor: hand;
}

div.code pre
{
font-family:    Monospace, Courier New, Courier;
font-size: 105%;
color:  #000000;
}

code
{
font-family:    Monospace, Courier New, Courier;
font-size: 105%;
color:  #000000;
}

dl
{
margin-top: 0;
padding-left:   1;
}

dd
{
margin-bottom:  0;
margin-left:    0;
padding-left:   20;
}

dd p
{
margin-top: 5;
}

ul
{
margin-left: 17;
list-style-type: disc;
}

ul ul
{
margin-bottom: 4;
margin-left: 17;
margin-top: 3;
list-style-type: disc;
}

ol
{
margin-left: 24;
list-style-type: decimal;
}

ol ol
{
margin-left: 24;
margin-top: 3;
list-style-type: lower-alpha;
}

li
{
margin-top: 0;
margin-bottom: 0;
padding-bottom: 0;
padding-top: 0;
margin-left: 5;
}

p
{
margin-bottom: 15;
}

.tip
{
color:  #0000FF;
font-style: italic;
cursor:hand;
text-decoration:underline;
}

.math
{
font-family: Times New Roman;
font-size: 125%
}
.sourceCodeList
{
font-family: Verdana;
font-size: 90%;
}

pre.viewCode
{
width: 100%;
overflow: auto;
}

li:hover table, li.over table
{
background-color: #C0C0C0;
}

li:hover ul, li.over ul
{
background-color: #d2d2d2;
border: 1px solid #000;
display: block;
}
            </style>
  </head>
  <body>
    <!--Topic built:08/03/2009 08:42:00-->

    
    
    
    
    
    
    
    
    
    <div id="header">
      <table width="100%" id="topTable"><tr>
          <td align="left">
            <span id="nsrTitle">Microsoft SQL Server 2008 R2 Release Notes: August 2009 CTP</span>
          </td>
          <td align="right">
            <span id="headfb" class="feedbackhead">
            </span>
          </td>
        </tr></table>
      
      
      
    </div>
    <div id="mainSection">
      <div id="mainBody"><p> 08/03/2009 08:42:00</p>
        
        <font color="DarkGray"> </font><p /> 
        <span id="changeHistory">
        </span>
    <p>This Release Notes document contains information for SQL Server 2008 R2 Community Technology Preview (CTP2) that supplements the SQL Server 2008 R2 CTP2 Readme and Books Online documentation. This document describes behaviors that apply only to this release or that are not documented in this release of Books Online.</p>
    <p>The Release Notes document is available only online. It is not available on the installation media. The Release Notes are updated periodically as required until the next release. The current version of this file is available on the <a href="http://go.microsoft.com/fwlink/?LinkID=155801" alt=""><linkText xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5">Release Notes</linkText></a> download page.</p>
    <p>For information about where to get assistance with installing SQL Server 2008 R2, consult the SQL Server 2008 R2 CTP2 Readme. The Readme is available from the <a href="http://go.microsoft.com/fwlink/?LinkId=157264" alt=""><linkText xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5">Readme</linkText></a> download page.</p>
    <p>
      <a href="#Top_of_page">[Top]</a>
    </p>
  <a name="Top_of_page" /><h1 class="heading">Contents</h1><div id="sectionSection0" class="section"><content xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5">
      <p xmlns="">
        <a href="#Before_You_Install">1.0 Before You Install</a>
      </p>
      <p xmlns="">
        <a href="#Database_Engine">2.0 Database Engine</a>
      </p>
      <p xmlns="">
        <a href="#Analysis_Services">3.0 Analysis Services</a>
      </p>
      <p xmlns="">
        <a href="#Integration_Services">4.0 Integration Services</a>
      </p>
      <p xmlns="">
        <a href="#Replication">5.0 Replication</a>
      </p>
      <p xmlns="">
        <a href="#Reporting_Services">6.0 Reporting Services</a>
      </p>
      <p xmlns="">
        <a href="#Service_Broker">7.0 Service Broker</a>
      </p>
      <p xmlns="">
        <a href="#Top_of_page">[Top]</a>
      </p>
    </content></div><a name="Before_You_Install" /><h1 class="heading">1.0 Before You Install</h1><div id="sectionSection1" class="section"><content xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5">
    </content><sections xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5">
      <h3 class="subHeading" xmlns="">1.1 Install .NET Framework 3.5 SP1 on "Gemini" Client First</h3><div class="subSection" xmlns=""><content xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5">
          <p xmlns="">You must install the .NET Framework 3.5 SP1 on a client computer before you install Office 2010 Technical Preview. If you installed Office first, uninstall it, install the .NET Framework 3.5 SP1 and then reinstall Office.</p>
        </content></div>
      <h3 class="subHeading" xmlns="">1.2 Reinstalling SQL Server 2008 Books Online After Upgrade May Display Incorrect Topic Heading</h3><div class="subSection" xmlns=""><content xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5">
          <p xmlns="">If you upgrade to SQL Server 2008 R2 Books Online from SQL Server 2008 with shared components including SQL Server Online, and later reinstall SQL Server 2008 Books Online, the default starting topic may appear with a SQL Server 2008 R2 heading. All other content is specific to SQL Server 2008, as expected.</p>
          <p xmlns="">Stand-alone installations of SQL Server 2008 Books Online that are upgraded to SQL Server 2008 R2 Books Online and later restored to SQL Server 2008 Books Online do not exhibit this behavior.</p>
          <p xmlns="">To avoid this problem, view the SQL Server 2008 R2 Books Online content online until you are certain you want to upgrade.</p>
        </content></div>
      <h3 class="subHeading" xmlns="">1.3 Do Not Customize Regional Language Settings Before Launching Setup</h3><div class="subSection" xmlns=""><content xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5">
          <p xmlns="">If you customize specific regional language settings, Setup will fail after launching.</p>
          <p xmlns="">This problem occurs if there is an inconsistency between the operating system language and the regional settings in the following situations:</p>
          <ul xmlns=""><li>
              For regional settings whose alphabets have letters composed of multiple characters that may also be separate letters in English words. (For example, the Czech alphabet has the letter "CH".)<br />
            </li><li>
              For languages that redefine the order of the characters in the Latin alphabet, thus affecting internal string sorting for Setup operations.(For example, in the Czech alphabet, "CH" sorts after H, unlike in English.)<br />
            </li></ul>
          <p xmlns="">To avoid this problem, set the regional settings to the operating system language before running Setup, and reset to their original values after Setup completes.</p>
        </content></div>
      <h3 class="subHeading" xmlns="">1.4 Do Not Upgrade from SQL Server 2008 on a Localized Operating System</h3><div class="subSection" xmlns=""><content xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5">
          <p xmlns="">Upgrade from SQL Server 2008 to SQL Server 2008 R2 CTP2 on a localized operating system fails and is not supported for CTP2.</p>
          <p xmlns="">The summary log indicates an error message similar to the following:</p>
          <p xmlns="">
            <code>2009-06-18 08:11:57 Slp: Error: Action "Microsoft.SqlServer.Configuration.RulesEngineExtension.RunRulesAction" threw an exception during execution.2009-06-18 08:11:57 Slp: Microsoft.SqlServer.Setup.Chainer.Workflow.ActionExecutionException: The Setup language is different than the language of the SQL Server features you are upgrading. To continue, use SQL Server Setup installation media of the same language as the installed SQL Server features. ---&gt;</code>
          </p>
          <p xmlns="">There is no solution or workaround for SQL Server 2008 R2 CTP2. This is a known issue and customers trying to follow this upgrade path are blocked.</p>
          <p xmlns="">
            <a href="#Top_of_page">[Top]</a>
          </p>
        </content></div>
    </sections></div><a name="Database_Engine" /><h1 class="heading">2.0 Database Engine</h1><div id="sectionSection2" class="section"><content xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5">
    </content><sections xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5">
      <h3 class="subHeading" xmlns="">2.1 Use sys.dm_sys_os_info to Determine the Time That SQL Server Has Spent Executing in Kernel and User Mode</h3><div class="subSection" xmlns=""><content xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5">
          <p xmlns="">The <notLocalizable xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5"><b xmlns="">sys.dm_os_sys_info</b></notLocalizable> dynamic management view contains two new columns: <notLocalizable xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5"><b xmlns="">process_kernel_time</b></notLocalizable> and <notLocalizable xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5"><b xmlns="">process_user_time</b></notLocalizable>. These columns show the total time in milliseconds that SQL Server has spent executing in kernel and user mode. To obtain this information, use these columns s instead of the @@CPU_BUSY and @@IO_BUSY functions.</p>
          <p xmlns="">We recommend that you avoid using the @@CPU_BUSY and @@IO_BUSY functions in new applications for the following reasons:</p>
          <ul xmlns=""><li>
              They show the elapsed time as a system dependent tick count. <br />
            </li><li>
              They support only 32-bit values and might wrap over an extended period of time, which causes inaccurate time estimates.<br />
            </li></ul>
          <p xmlns="">
            <a href="#Top_of_page">[Top]</a>
          </p>
        </content></div>
    </sections></div><a name="Analysis_Services" /><h1 class="heading">3.0 Analysis Services</h1><div id="sectionSection3" class="section"><content xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5">
    </content><sections xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5">
      <h3 class="subHeading" xmlns="">3.1 Do Not Install Analysis Services on a Failover Cluster</h3><div class="subSection" xmlns=""><content xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5">
          <p xmlns="">In SQL Server 2008 R2 CTP2, you cannot install Analysis Services in a failover cluster.</p>
        </content></div>
      <h3 class="subHeading" xmlns="">3.2 Do Not Install Analysis Services on Windows XP</h3><div class="subSection" xmlns=""><content xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5">
          <p xmlns="">Analysis Services is not supported on Microsoft Windows XP. You will not receive an error during installation, but certain operations (such as database restore) will fail. </p>
          <p xmlns="">Note that this restriction applies only to Analysis Services server instances, and not to the "Gemini" add-in for Excel. Windows XP is supported for the "Gemini" client application.</p>
        </content></div>
      <h3 class="subHeading" xmlns="">3.3 Copying PivotTables or PivotCharts Is Not Supported</h3><div class="subSection" xmlns=""><content xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5">
          <p xmlns="">Copying a PivotTable or PivotChart and pasting it anywhere in the Excel workbook will cause the original to no longer work. Instead of copying, use the Insert PivotTable command or button to create a new PivotTable or PivotChart and build another report by adding fields to the drop zones.</p>
        </content></div>
      <h3 class="subHeading" xmlns="">3.4 "Gemini" Server</h3><div class="subSection" xmlns=""><content xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5">
        </content><sections xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5">
          <h4 class="subHeading" xmlns="">3.4.1 Do Not Install "Gemini" on a Drive with Limited Free Space</h4><div class="subSection" xmlns=""><content xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5">
              <p xmlns="">If a large number of workbooks are loaded within a 14-day period, you might run out of disk space. To avoid this problem, install "Gemini" on a drive with a large amount of available space.</p>
            </content></div>
          <h4 class="subHeading" xmlns="">3.4.2 Do Not Reuse Database Names for "Gemini" Service Applications</h4><div class="subSection" xmlns=""><content xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5">
              <p xmlns="">When you create a new "Gemini" service application in Central Administration, do not reuse database names that were created for other "Gemini" service applications. Even if you delete both the service application and the database, the credentials that you used for the first service application will be reused. To workaround this problem, choose a new database name each time you create a "Gemini" service application.</p>
            </content></div>
          <h4 class="subHeading" xmlns="">3.4.3 Excel Services Issues</h4><div class="subSection" xmlns=""><content xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5">
              <p xmlns="">Excel Services must be enabled for a "Gemini" installation. To enable Excel Services, you must have the required permissions.</p>
            </content><sections xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5">
              <h5 class="subHeading" xmlns="">Verify Permissions for Enabling Excel Services</h5><div class="subSection" xmlns=""><content xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5">
                  <p xmlns="">You must have both farm administrator permissions and SQL Server administrative permissions on the Database Engine instance that hosts the configuration database. Run the following PowerShell command to verify that Excel Services is enabled and that you have permission to configure it:</p>
                  <p xmlns="">
                    <b>PS C:\Windows\system32&gt; Add-PSSnapin Microsoft.SharePoint.PowerShell</b>
                  </p>
                  <p xmlns="">
                    <b>PS C:\Windows\system32&gt; get-help *SPExcel*</b>
                  </p>
                  <p xmlns="">If the command does not generate a list of PowerShell commands supported by Excel Services, either the feature is not enabled or you do not have permission to configure the service.</p>
                </content></div>
              <h5 class="subHeading" xmlns="">Enable and Configure Excel Services for "Gemini"</h5><div class="subSection" xmlns=""><content xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5">
                  <p xmlns="">Excel Services is required for a "Gemini" installation. If you install "Gemini" on an existing SharePoint server that does not have Excel Services enabled, you must enable and configure Excel Services before you can use "Gemini" features. </p>
                  <p xmlns="">Use Central Administration to verify that Excel Services is enabled. Use PowerShell script to create and configure an Excel Services service application for use with a "Gemini" installation.</p>
                  <p xmlns="">In Central Administration, click <b>System Settings</b>, click <b>Farm Management</b>, and then click <b>Manage farm features</b> to verify that Excel Services is enabled in the farm.</p>
                  <p xmlns="">To run the following Windows PowerShell script to create and configure:</p>
                  <p xmlns="">On the Start Menu, point to <b>All Programs</b>, and click <b>Windows PowerShell 1.0</b>.</p>
                  <p xmlns="">Right-click <b>Windows Powershell</b>, click <b>Run as administrator</b>, and enter the following commands:</p>
                  <p xmlns="">
                    <b>Add-PSSnapin Microsoft.SharePoint.Powershell New-SPExcelServiceApplication -name ExcelServiceApp1 -Default -SPIisWebServiceApplicationPool 'SharePoint Web Services System Default'</b>
                  </p>
                  <p xmlns="">
                    <b>Set-SPExcelServiceApplication -identity 'ExcelServiceApp1' -AccessModel delegation Set-SPExcelFileLocation -ExternalDataAllowed 2 -WorkbookSizeMax 50 -WarnOnDataRefresh:$false -ExcelServiceApplication 'ExcelServiceApp1' -identity 'http://'</b>
                  </p>
                </content></div>
            </sections></div>
          <h4 class="subHeading" xmlns="">3.4.4 Ensure That "Gemini" Services Are in the Same State</h4><div class="subSection" xmlns=""><content xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5">
              <p xmlns="">"Gemini" is implemented as a Windows service and Web service that must be run together. If you do not enable, disable, start, or stop them as a pair, the system may return unexpected errors. For example, if the "Gemini" middle-tier service is enabled while its engine service is disabled, the middle-tier service will repeatedly send load database commands to the engine server, even though the engine service is not available. </p>
              <p xmlns="">To ensure coordinated server operations, manage the services together by having them share the same state.</p>
            </content></div>
          <h4 class="subHeading" xmlns="">3.4.5 Use SharePoint Central Administration for Managing "Gemini" Services</h4><div class="subSection" xmlns=""><content xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5">
              <p xmlns="">In SQL Server 2008 R2, you must use SharePoint Central Administration to start or stop services to ensure both services share the same state. Do not use SQL Server Configuration Manager or the Services console application to disable or restart the Analysis Services engine service for a "Gemini" deployment. Similarly, do not use IIS Manager to restart or stop the "Gemini" service. </p>
            </content></div>
          <h4 class="subHeading" xmlns="">3.4.6 Ensure That Administrator Permissions Are Granted for the "Gemini" Service</h4><div class="subSection" xmlns=""><content xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5">
              <p xmlns="">The "Gemini" service application must have administrator permissions to access the local "Gemini" engine service. To grant administrator access to the "Gemini" engine service, use SQL Server Management Studio. Alternatively, you can use SharePoint Central Administration to configure both the "Gemini" service identity and the Engine service account to use the same Windows user account. Configuring both services to run under the same identity ensures that both services have correct access.</p>
            </content></div>
          <h4 class="subHeading" xmlns="">3.4.7 Do Not Use Personal Windows User Accounts to Run "Gemini" Services</h4><div class="subSection" xmlns=""><content xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5">
              <p xmlns="">Do not use your personal Windows user account to run either of the "Gemini" services or any service in a SharePoint farm. Doing so increases the threat of unauthorized access to server operations or data. This is especially true if you do not enable Secure Store for your SharePoint farm or server. Without Secure Store and predefined target application IDs, your user account provides security context that the "Gemini" middle-tier service uses to connect to external data sources during data refresh operations. Because information workers typically have more permissions than services require, it is strongly recommended that you avoid using your personal account for "Gemini" services.</p>
            </content></div>
          <h4 class="subHeading" xmlns="">3.4.8 Report Gallery Returns Error If the Server URL Is Already Mapped to a Web Content Zone</h4><div class="subSection" xmlns=""><content xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5">
              <p xmlns="">Before Report Gallery renders a thumbnail of a report or worksheet, it attempts to add the server URL to the trusted site web content zone using the built-in capabilities of Internet Explorer. If the server URL is already mapped to a different zone (such as Local Intranet), Report Gallery will generate a "File Already Exists" error (-2147024816) and the thumbnail will not be created. To work around this issue, delete the server URL from the other zone.</p>
            </content></div>
          <h4 class="subHeading" xmlns="">3.4.9 Excel Services Returns an Error When Viewing a Published "Gemini" Workbook</h4><div class="subSection" xmlns=""><content xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5">
              <p xmlns="">In CTP2, users that have view-only access to a "Gemini" workbook will be able to render the workbook in Excel Services, but any operation that refreshes the connection will fail with an "access denied" error.</p>
            </content></div>
          <h4 class="subHeading" xmlns="">3.4.10 Adding a Server to a "Gemini" SharePoint Farm Requires AMO Library</h4><div class="subSection" xmlns=""><content xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5">
              <p xmlns="">If you try to add a server to a SharePoint Farm with "Gemini" configured, the attempt fails with the following error: </p>
              <p xmlns="">
                <code>Could not load file or assembly 'Microsoft.AnalysisServices, Version=10.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.</code>
              </p>
              <p xmlns="">The error occurs because the new server does not have the Microsoft Analysis Services Management Objects (AMO) library that the Gemini service application requires. To work around this issue, download the AMO library from the <a href="http://go.microsoft.com/fwlink/?LinkId=158926" alt=""><linkText xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5">SQL Server 2008 Feature Pack</linkText></a> download page, and then re-run the SharePoint Configuration Wizard.</p>
            </content></div>
          <h4 class="subHeading" xmlns="">3.4.11 Permission Requirements for Generating Thumbnails in Report Gallery</h4><div class="subSection" xmlns=""><content xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5">
              <p xmlns="">Report Gallery uses web server and browser capabilities to generate thumbnail images. Permissions that allow thumbnail generation are configured automatically, but if you later change the application pool identity of a SharePoint web application in Internet Information Services (IIS), it can disrupt thumbnail image creation in Report Gallery.</p>
              <p xmlns="">To get thumbnail images back on the page, grant Full Read Access to the new service account in the web application's user policies. To do this, open <b>Manage Web Applications</b> in Central Administration. Click <b>User Policy</b>, click <b>Add Users</b>, select <b>Full Read</b>, and then click <b>Finish</b>.</p>
            </content></div>
        </sections></div>
      <h3 class="subHeading" xmlns="">3.5 "Gemini" Models and the "Gemini" Client Application</h3><div class="subSection" xmlns=""><content xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5">
        </content><sections xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5">
          <h4 class="subHeading" xmlns="">3.5.1 Do Not Use Models Created Using This Release of "Gemini" in Later Releases</h4><div class="subSection" xmlns=""><content xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5">
              <p xmlns="">Once you have installed a future release of "Gemini", you will not be able to open or modify any .xslx file with embedded "Gemini" data created by using the SQL Server 2008 R2 release of "Gemini".</p>
              <p xmlns="">If you are creating a "Gemini" model that you want to use in a future release of "Gemini", make sure that you are retaining all data sources and documenting the steps required to build the model. Doing so will enable you to re-create the model using a later release of "Gemini." </p>
            </content></div>
          <h4 class="subHeading" xmlns="">3.5.2 Avoid Building an Excel 2010 Slicer on a DATETIME Column</h4><div class="subSection" xmlns=""><content xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5">
              <p xmlns="">If you create a Slicer on a column that contains data of the DATETIME data type, you might receive an error that indicates that an object cannot be found. </p>
              <p xmlns="">To avoid this problem, you can create a calculated column that extracts appropriate elements of the DATETIME data type (year, month, day, hour, minute, seconds), and composes them into another date or string. An example of such expressions are: </p>
              <p xmlns="">=Date(Year([OriginalDateTimeColumn]), Month([OriginalDateTimeColumn]), Day([OriginalDateTimeColumn]))</p>
              <p xmlns="">=MONTH([OriginalDateTimeColumn]) &amp; "/" &amp; DAY([OriginalDateTimeColumn]) &amp; "/" &amp; Year([OriginalDateTimeColumn]) &amp; " " &amp; HOUR([OriginalDateTimeColumn]) &amp; ":" &amp; MINUTE([OriginalDateTimeColumn]) &amp; ":" &amp; SECOND([OriginalDateTimeColumn])</p>
            </content></div>
          <h4 class="subHeading" xmlns="">3.5.3 Excel Slicers Feature Does Not Work on Computers with non-English Configuration Options</h4><div class="subSection" xmlns=""><content xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5">
              <p xmlns="">In CTP2, adding slicers to a worksheet is not supported on a computer that has display configuration options for dates, times, and numbers different from English (United States). To use slicers, please save your work, close Excel, set the computer display configuration options to English (US), and then restart Excel. </p>
              <p xmlns="">To set the computer display configuration options, on the Start menu, click <b>Run</b>, type <b>intl.cpl</b> and click <b>OK</b>. Select <b>English (United States)</b> from the <b>Format</b> list, and click <b>OK</b>.</p>
            </content></div>
          <h4 class="subHeading" xmlns="">3.5.4 Edit the Definition of a Calculated Column If You Make Any Changes to the Definition of Underlying Measures</h4><div class="subSection" xmlns=""><content xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5">
              <p xmlns="">If you create a calculated column that is based on a measure, and the formula that defines the measure changes in any way, the calculated column is not automatically recalculated to show the new values. Therefore, the column will continue to show the old values as if the measure’s formula had never been updated.</p>
              <p xmlns="">To ensure that values in the calculated column are recalculated, you must edit the formula for the calculated column and thereby trigger a recalculation of the column. You can also avoid this issue by never referring to a measure in the formula for a calculated column. </p>
            </content></div>
          <h4 class="subHeading" xmlns="">3.5.5 Smart Tag Option for Adding Calculated Column Is Not Fully Implemented</h4><div class="subSection" xmlns=""><content xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5">
              <p xmlns="">In general, if any cells within a column contain text data, the entire column will be treated as text, and the column cannot be used in calculations, nor can it be added to the values field in the Gemini fields list when creating PivotTables. </p>
              <p xmlns="">In CTP2, if you paste a column less than 5 percent of whose values are text, you will see a smart tag option. Choosing this option will automatically add a calculated column that converts the text values to null, so they can now be used for calculations. In CTP2, however, the actual calculated column will not be added, because the feature is only partly implemented. The functionality is expected to be fully implemented in a future CTP. </p>
              <p xmlns="">In CTP2, you can work around  this issue in two ways. You can modify the original data to ensure that all cells within the column contain numeric data before importing the table into a Gemini model. Alternatively, you can copy individual rows into a separate worksheet or Gemini table, change the text data to numeric data, and then copy the changed rows back into the workspace. </p>
            </content></div>
          <h4 class="subHeading" xmlns="">3.5.6 Known Issues When Pasting Data from Excel into a "Gemini" Model</h4><div class="subSection" xmlns=""><content xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5">
            </content><sections xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5">
              <h5 class="subHeading" xmlns="">Pasting Truncated Data</h5><div class="subSection" xmlns=""><content xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5">
                  <p xmlns="">Content copied from Excel must be fully visible when you copy it. If values appear as hash (###) characters, the entire column will be pasted into "Gemini" as text. To work around this issue, widen the column so that all values are fully visible before copying the data into "Gemini" model.</p>
                </content></div>
              <h5 class="subHeading" xmlns="">Pasting Empty Cells When Data Is Formatted with a Border Style</h5><div class="subSection" xmlns=""><content xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5">
                  <p xmlns="">When copying Excel data that has border styles, empty cells are detected as text, causing the entire column to be pasted as text. To work around this issue, either remove the border lines, or ensure that all cells contain values or a space.</p>
                </content></div>
              <h5 class="subHeading" xmlns="">Pasting Cell Values Overlapping Adjacent Empty Cells</h5><div class="subSection" xmlns=""><content xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5">
                  <p xmlns="">When pasting the data selection into "Gemini", if values in one cell overlap an adjacent empty cell, the second column is not detected as a separate column and will be skipped. If you paste multiple columns and only one row has overlapping columns, the paste operation will fail since the number of columns in each row are not identical. To work around this issue, widen the columns so that no overlapping occurs, or wrap the content so that the entire value fits within the boundary of the cell.</p>
                </content></div>
            </sections></div>
          <h4 class="subHeading" xmlns="">3.5.7 Known Issues with the "Gemini" Task Pane</h4><div class="subSection" xmlns=""><content xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5">
            </content><sections xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5">
              <h5 class="subHeading" xmlns="">Excel 2010 Named Sets Do Not Appear in the Task Pane</h5><div class="subSection" xmlns=""><content xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5">
                  <p xmlns="">Named sets that you create in Excel 2010 are not supported in the "Gemini" Task Pane. This means that they do not appear in the "Gemini" Field List and cannot be used to create PivotTables or PivotCharts that are based on "Gemini" data.</p>
                </content></div>
              <h5 class="subHeading" xmlns="">The Task Pane Disappears When Deleting a Named Set</h5><div class="subSection" xmlns=""><content xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5">
                  <p xmlns="">A second known issue is that the "Gemini" Task Pane will temporarily disappear when you delete a named set that was created through MDX that references values from the "Gemini" Task Pane. Click anywhere in the PivotTable or PivotChart to make the "Gemini" Task Pane reappear.</p>
                </content></div>
            </sections></div>
          <h4 class="subHeading" xmlns="">3.5.8 Known Issues with Dates and Times</h4><div class="subSection" xmlns=""><content xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5">
            </content><sections xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5">
              <h5 class="subHeading" xmlns="">Working with Dates and Times</h5><div class="subSection" xmlns=""><content xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5">
                  <p xmlns="">In general, DAX date and time functions work with dates as a <b>datetime</b> data type, not as serial numbers like Microsoft Excel does. Therefore, if a DAX formula returns a date, that date is treated by Excel as a date. Excel formatting can then be applied to change the date to any desired format, including a serial number.</p>
                </content></div>
              <h5 class="subHeading" xmlns="">Limitations on Dates and Times</h5><div class="subSection" xmlns=""><content xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5">
                  <p xmlns="">DAX formulas support the use of dates beginning with March 1, 1900. For dates before March 1, 1900, the same limitations apply that are present in Excel.</p>
                  <p xmlns="">If a column in a "Gemini" workbook contains <b>datetime</b> data and that column is used in a PivotTable, Excel treats the date values as attribute members, not as measures. As a consequence, Excel uses the value of the column's Caption property, rather than actual date values; these dates cannot be reformatted by using Excel formatting.  </p>
                </content></div>
            </sections></div>
          <h4 class="subHeading" xmlns="">3.5.9 Administrator Permissions Required</h4><div class="subSection" xmlns=""><content xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5">
              <p xmlns="">To use the "Gemini" add-in on your workstation, you must either have administrator permissions on the computer or "Lock pages in memory" permission.</p>
            </content></div>
          <h4 class="subHeading" xmlns="">3.5.10 "Gemini" Add-in for Excel Is Not Compatible with the Data Mining Add-in for Excel</h4><div class="subSection" xmlns=""><content xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5">
              <p xmlns="">In CTP2, the "Gemini" Add-in is not compatible with either the SQL Server 2008 or SQL Server 2008 R2 versions of the Data Mining add-in. Installing both add-ins will limit some "Gemini" features, including the ability to import data. </p>
              <p xmlns="">If you already installed the Data Mining add-in, uninstall it and restart Excel.</p>
            </content></div>
          <h4 class="subHeading" xmlns="">3.5.11 Do Not Import Text Columns That Exceed 1,024 Characters</h4><div class="subSection" xmlns=""><content xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5">
              <p xmlns="">If you use the Import Wizard to import data from SQL Server or Access databases, table columns of VARCHAR(MAX), NVARCHAR(MAX), or MEMO types will cause a table import to fail with truncation errors if the table contains rows that are equal to or greater than 1,024 characters.</p>
              <p xmlns="">This issue might also occur for other databases and data types if the provider used to connect from the Import Wizard returns an unknown maximum size for text columns that exceed 1,024 characters.</p>
              <p xmlns="">To work around this limitation, use the Import Wizard's Filter and Preview window to uncheck individual columns that will cause the import to fail. Alternatively, you can use the Import Wizard’s Custom Query feature to write a SQL statement that truncates the contents of problematic columns prior to sending them to the in-memory engine, thus preventing automatic truncation, and the resulting error to occur.</p>
              <p xmlns="">This issue does not apply to fixed-size VARCHAR and NVARCHAR types in SQL Server.</p>
              <p xmlns="">
                <a href="#Top_of_page">[Top]</a>
              </p>
            </content></div>
        </sections></div>
    </sections></div><a name="Integration_Services" /><h1 class="heading">4.0 Integration Services</h1><div id="sectionSection4" class="section"><content xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5">
    </content><sections xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5">
      <h3 class="subHeading" xmlns="">4.1 Do Not Run Utility Information Collection Set from an Unmanaged Instance of SQL Server</h3><div class="subSection" xmlns=""><content xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5">
          <p xmlns="">If you start data collection sets using the Configure Management Data Warehouse wizard in SQL Server Management Studio for a SQL Server instance that is not managed by a utility control point (UCP), the utility information collection set will fail to run. Integration Services errors for the utility information collection set are generated and visible in the Log File Viewer for System Data Collection Sets.</p>
          <p xmlns="">The utility information collection set can be stopped in SQL Server Management Studio by right-clicking the utility information collection set under System Data Collection Sets and selecting Stop Data Collection Set.</p>
          <p xmlns="">
            <a href="#Top_of_page">[Top]</a>
          </p>
        </content></div>
    </sections></div><a name="Replication" /><h1 class="heading">5.0 Replication</h1><div id="sectionSection5" class="section"><content xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5">
      <p xmlns="">There are no notes for this component in this release of SQL Server 2008 R2.</p>
      <p xmlns="">
        <a href="#Top_of_page">[Top]</a>
      </p>
    </content></div><a name="Reporting_Services" /><h1 class="heading">6.0 Reporting Services</h1><div id="sectionSection6" class="section"><content xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5">
    </content><sections xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5">
      <h3 class="subHeading" xmlns="">6.1 Atom Rendering Extension Does Not Work After Upgrading to SQL Server 2008 R2 Reporting Services</h3><div class="subSection" xmlns=""><content xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5">
          <p xmlns="">After you upgrade an instance of SQL Server 2008 Reporting Services to SQL Server 2008 R2 Reporting Services, exporting reports as data feeds fails. This is because the configuration setting for the Atom rendering extension is missing in the report server configuration file, RSReportServer.config. </p>
          <p xmlns="">To correct the problem, add the following entry to the <b>&lt;Render&gt;</b> element in the configuration file, RSReportServer.config. </p>
          <p xmlns="">
            <b>&lt;Extension Name="ATOM" Type="Microsoft.ReportingServices.Rendering.DataRenderer.AtomDataReport,Microsoft.ReportingServices.DataRendering" /&gt;</b>
          </p>
          <p xmlns="">By default, the configuration file is in C:\Program Files\Microsoft SQL Server\MSRS10_50.MSSQLSERVER\Reporting Services\ReportServer. Before you change the configuration file, we recommend that you make a copy of the file.</p>
        </content></div>
      <h3 class="subHeading" xmlns="">6.2 Do Not Select Reporting Services on the Failover Cluster Feature Selection Page</h3><div class="subSection" xmlns=""><content xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5">
          <p xmlns="">When installing SQL Server Failover Cluster, if you select Reporting Services on the Feature Selection page, you will receive the error, "A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible."</p>
          <p xmlns="">To avoid the problem, do not select the Reporting Services feature on the Feature Selection page when setting up SQL Server Failover Cluster. Reporting Services can be installed separately after the failover cluster installation is complete.</p>
        </content></div>
      <h3 class="subHeading" xmlns="">6.3 Reporting Services Setup Fails If SharePoint Server 2010 Is Already Installed</h3><div class="subSection" xmlns=""><content xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5">
          <p xmlns="">When attempting to install SQL Server 2008 R2 Reporting Services on a computer that has SharePoint Server 2010 installed, the user will see the following error message and installation fails: </p>
          <p xmlns="">
            <code>Attempted to read or write protected memory. This is often an indication that other memory is corrupt.</code>
          </p>
          <p xmlns="">This occurs when the operating system is Windows Server 2008.</p>
          <p xmlns="">To avoid this problem, before installing SQL Server 2008 R2 Reporting Services, install the appropriate hotfix from the list in KB article <a href="http://go.microsoft.com/fwlink/?LinkId=158986" alt=""><linkText xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5">953290</linkText></a>, "An application may crash when it uses legacy methods to query performance counter values in Windows Vista or in Windows Server 2008." </p>
        </content></div>
      <h3 class="subHeading" xmlns="">6.4 SharePoint Server 2010 Central Administration Page Displays an Error Message After Configuring the Report Server URL</h3><div class="subSection" xmlns=""><content xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5">
          <p xmlns="">On the SharePoint Server 2010 Central Administration page, a user can enter the report server URL and user name/password, and complete the configuration of SharePoint integrated mode. </p>
          <p xmlns="">However, the page redirects to a summary page and displays the following error message because the file needed to properly display the successful configuration results is not available. </p>
          <p xmlns="">
            <code>The file '/_layouts/ReportServer/RSIntegrationResults.aspx' does not exist.</code>
          </p>
          <p xmlns="">The configuration is successful; the error message pertains to a problem displaying the summary page upon successful configuration.</p>
          <p xmlns="">There is currently no workaround. </p>
        </content></div>
      <h3 class="subHeading" xmlns="">6.5 Reporting Services Is Not Listed As an Option in the SharePoint Server 2010 Enable Features Page</h3><div class="subSection" xmlns=""><content xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5">
          <p xmlns="">You might not be able to enable Reporting Services from the SharePoint Server 2010 management pages because Reporting Services is not listed as an option. </p>
          <p xmlns="">To work around this issue, use the SharePoint Services administrative application STSADM.EXE to activate Reporting Services. The following is an example of the command line syntax: </p>
          <p xmlns="">
            <b>%SystemDrive%\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN\STSADM.EXE" -o activatefeature -n ReportServer -url http:// ://&lt;hostname&gt;:&lt;SharePointCAPort&gt;</b>
          </p>
          <p xmlns="">
            <a href="#Top_of_page">[Top]</a>
          </p>
        </content></div>
    </sections></div><a name="Service_Broker" /><h1 class="heading">7.0 Service Broker</h1><div id="sectionSection7" class="section"><content xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5">
      <p xmlns="">There are no notes for this component in this release of SQL Server 2008 R2.</p>
      <p xmlns="">
        <a href="#Top_of_page">[Top]</a>
      </p>
    </content></div><!--[if gte IE 5]>
			<tool:tip element="seeAlsoToolTip" avoidmouse="false"/><tool:tip element="languageFilterToolTip" avoidmouse="false"/><tool:tip element="roleInfoSpan" avoidmouse="false"/>
		<![endif]--></div>
      <div id="footer">
			
			© 2008 Microsoft Corporation. All rights reserved.
		</div>
    </div>
  </body>
</html>